• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    method and system for diagnosing a fault or an open circuit in a network a fault injection circuit (34) injects a test signal into a data bus (17) with a normal low logic level. the test signal has a higher logic level, greater than the normal high logic level of the data bus (17) or a lower logic level lower than the normal low logic level of the data bus (17). an analog to digital converter (36) is coupled to a voltage level detector (35) to detect an aggregate level of an aggregate signal on the data bus (17). the aggregate signal is composed of the terminating circuit signal is the test signal. a diagnostic tool (10) determines whether a fault connection between the data bus (17) and a network device (44,144,244) exists, where the detected aggregate level exceeds at least a normal low logic level
    公开号:BR112013015404B1
    申请号:R112013015404-7
    申请日:2011-12-16
    公开日:2020-09-24
    发明作者:David C. Smart；Michael R. Schlichtmann；Ronald G. Landman
    申请人:Deere & Company；
    IPC主号:
    专利说明:

    [0001] [001] This invention refers to a method and system for diagnosing a fault or an open circuit in a network. Knowledge
    [0002] [002] In the prior art, a means of transport or equipment can be configured with a Controller Area Network (CAN) data bus or another network data bus that supports communication between controllers and other network elements. The means of transport data bus communicates signals over a transmission line, such as one or more twisted pairs or coaxial wire or cable, for example. If the transmission line is cut or damaged, communications over the network data bus may be strange, intermittent, or absent. Physical visual inspection of the transmission line may not be practical or possible where the cable is routed through conduit, sheath, frame members, single chassis means of transport structures, chassis panels, or other equipment structures. Therefore, there is a need for an alternative method and system for diagnosing a fault or an open circuit in a network. Summary of the Invention
    [0003] [003] According to a modality, a method and system is able to diagnose a fault or an open circuit in a network (eg, transport network). The network comprises a network data bus and one or more network elements. The network data bus has a normal high logic level and a normal low logic level consistent with a termination circuit signal applied by said one or more network elements. A fault injection circuit is adapted to inject a test signal into a network data bus over a period of test time. The test signal has at least one of a higher logic level, greater than the normal high logic level of the data bus or the lowest logic level, less than the normal low logic level of the data bus. An analog to digital converter is coupled to a detector (eg, voltage level detector) to sense an aggregate level of an aggregate signal on a network data bus. The aggregate signal is composed of the terminating circuit signal and the test signal. A diagnostic tool indicates whether a fault connection between the data bus and a network device exists, where a fault connection results in the sensed aggregate level of the detector exceeding at least one of the normal high logic level and the normal low logic level . Brief Description Of Drawings
    [0004] [004] FIG. 1 is a block diagram of a modality of a system for diagnosing a fault or an open circuit in a network.
    [0005] [005] FIG. 2 is a flow chart of an embodiment of a method for diagnosing a fault or an open circuit in a network.
    [0006] [006] FIG. 3 is a diagram illustrating data communication messages between a diagnostic tool and network elements in a network to facilitate one or more diagnostic tests.
    [0007] [007] FIG. 4A is a diagram of an example network hardware that illustrates an open circuit on a second node.
    [0008] [008] FIG. 4B is a diagram of a signal magnitude versus time on a network data bus.
    [0009] [009] FIG. 5A and FIG. 5B provides functional status diagrams for diagnostic software (eg, remote diagnostic software, primary diagnostic software or both). Description of the Preferred Modality
    [0010] [0010] In Fig. 1, according to one modality, a system 11 is configured to diagnose a fault or an open circuit in a network 26. Network 26 can refer to a means of transport network, an implementation network , a subnet, a transport network subnet, a subnet of an implementation network, or any other network. System 11 comprises a network 26, a main structure of network 16 (e.g., data bus of network 17), one or more network elements (28, 30, 32), a fault injection circuit 34, a detector 35, and analog to digital converter 36, and a diagnostic tool 10. At least one network element (28, 30, 32) comprises a fault injection circuit 34, a detector 35 and an analog to digital converter 36. The diagnostic tool 10 is coupled to the data network 26. The diagnostic tool 10 and the network elements (28, 30, 32) are able to communicate via the network data bus 17, of the main structure of the network 16, or an auxiliary data bus of network 26.
    [0011] [0011] In one embodiment, network 26 comprises a main structure of network 16 and one or more network elements (28, 30, 32). For example, a main structure of network 16 may comprise one or more of the following: a network data bus 17, a means of transport data bus, a data bus, or a Controller Area Network data bus (CAN). A network data bus 17 comprises a physical data path, a logical data path (e.g., virtual data path), or both. The network data bus 17 provides one or more data paths that support data communications between a source and a destination, for example.
    [0012] [0012] Network 26 has a network architecture that refers to the underlying physical structure and data structure of network 26. The structure of physical network 26 can be referred to as a main structure of network 16. The main structure of network 16 of network 26 can comprise transmission line for network data bus 17, connectors, interfaces matching impedance, amplifiers, repeaters, filters, splitters, combination devices, terminations, tips, interfaces and hardware, for example. The data structure of network 26 can comprise functional layers, interfaces and protocols to support data communications (eg, without unresolved conflict) between network elements (28, 30, 32) over a network data bus 16 .
    [0013] [0013] The transmission line of network 26 may comprise one or more twisted pairs, cord cable, multi-conductor cable, shielded multi-conductor cable, a coaxial cable, optical cable, a wiring harness, or another streaming. In a network configuration, a network data bus 17 or main structure of network 16 is associated with one or more digital logic levels. For example, a network data bus 17 or main structure of network 16 has a normal high logic level and a normal low logic level consistent with a termination circuit signal applied by said one or more network elements (28) , 30, 32) of network 26.
    [0014] [0014] Each network element (28, 30, 32) is associated with a node (18, 20, 22) or node identifier, where the network element is coupled or connected to a network data bus 17. Each The network element (28, 30, 32) can comprise a controller 38, an actuator, a sensor, a communications device, or another electronic device. For example, a motor controller, a transmission controller, or a combination of the controller (eg, combined motor controller and transmission controller) can be connected to a network 26 for communication with other network elements (28, 30 , 32) via network 26.
    [0015] [0015] In one embodiment, the first network element 28 comprises a first network element device 44, an analog to digital converter 36, a detector 35, and a fault injection circuit 34. The first network element device network 44 comprises a transceiver 46 (eg, CAN transceiver) coupled to controller 38. transceiver 46 is coupled to a main structure of network 16 (eg, network data bus 17) and network 26 to provide a communications interface between the first network element device 44 and network 26 or main structure of network 16.
    [0016] The controller 38 comprises a data processor 48 and a data storage device 40 coupled to a data bus 50. The data processor 48 may comprise a microprocessor, a microcontroller, a programmable logic matrix, a specific integrated circuit application, or another electronic device to process or manipulate data. The data storage device 40 stores or contains remote diagnostic software 42. The data storage device 40 comprises electronic memory (eg, non-volatile random access memory), an optical storage device, a magnetic storage device , a magnetic disk controller, or another device for storing, retrieving and managing electronic data.
    [0017] [0017] Remote diagnostic software 42 can reside on data storage device 40 (eg, electronic memory) of the network device element or on transceiver 46. For example, remote diagnostic software 42 may be stored on data storage device 40 for depositing non-transient data or on technologically similar data storage devices on transceiver 46. A data processor 48 of the network element device or a technically similar data processor on transceiver 46 can run the software remote diagnostics 42. In one embodiment, the analog to digital converter 36 provides an interface between a main structure of network 16 and remote diagnostics software 42. Conversely, fault injection circuit 34 provides an interface between the diagnostic software remote 42 and a main network structure 16. Remote diagnostic software 42 and its interface can use or control h ardware that is associated with transceiver 46, the first network element device 44, or both.
    [0018] [0018] Fault injection circuit 34 is capable of communicating with remote diagnostic software 42. Fault injection circuit 34 can comprise fault injection logic and an isolated voltage supply (or current source) for providing a test signal during a test interval, where the test signal may comprise a voltage pulse, a generally rectangular wave, a substantially square wave, a pulse train, or other suitable test signal. Fault injection circuit 34 is configured or adapted to inject a test signal into a network data bus 17, a main structure of network 16, or secondary transmission lines 24 of network 26 during a test time period.
    [0019] [0019] In a first example, the fault injection circuit 34 can inject a test signal into a network data bus 17 of the network 26 via an impedance bridge or a resistive interface (eg, pull- up) with high impedance with respect to a network data bus 17. In a second example, fault injection circuit 34 can inject a test signal into a network data bus 17 of network 26 via transceiver 46 In one configuration, the test signal has at least one of a higher logic level, greater than the normal high logic level of the network data bus 17 or a lower logic level, less than the normal low logic level of the bus network data 17. Fault injection circuit 34 represents a diagnostic enhancement that is not found in many commercially available network elements that are suitable for interfacing with network data bus 17, for example.
    [0020] [0020] In one configuration, if a network data bus 17 comprises a CAN data bus, a normal high logic level is approximately 3.5 volts direct current (DC) and the normal logic level is approximately 1.5 volts of direct current (DC). In addition, if a network data bus 17 comprises a CAN data bus, in certain configurations, the test signal has a higher logic level, equal to approximately 5 volts direct current (DC) and a lower logic level equal to approximately 0 volts of direct current (DC).
    [0021] [0021] In one embodiment, detector 35 (eg, voltage level detector) is coupled as an intermediate circuit between a network data bus 17 and analog to digital converter 36. Detector 35 may comprise a comparator (eg, operational amplifier) with a reference voltage applied to one input and the aggregate voltage of the network data bus 17 applied to another input, via an input resistor or the other way around.
    [0022] [0022] The output of detector 35 (eg, comparator) can be coupled to an input of the analog to digital converter 36, or dimensioned with a voltage divider or voltage scaling circuit before an application for an input of the analog to digital converter 36.
    [0023] [0023] An analog to digital converter input 36 is coupled to detector 35 (eg, voltage level detector) to detect an aggregate level of an aggregate signal on a network data bus 17. An output of the analog to digital converter 36 is coupled to controller 38, or to the network element device (44, 144, or 244). The aggregate signal is composed of the terminating circuit signal and the test signal. For example, one or more network elements (28, 30, 32) provide or apply the termination circuit signal to a network data bus 17 during normal operation, where the termination circuit signal can comprise one or more of the following, a data packet (eg, Controller Area Network (CAN) data packet), a data message, an idle signal, an idle data message, a low logic level signal, a high logic level, a bias signal (eg, a voltage level between a normal high logic level signal and a normal low logic level signal). The test signal is larger than a high logic level signal, smaller than the low logic level signal, or conversely can be distinguished from the terminating circuit signal in frequency, time span, pulse duration , pulse shape, waveform magnitude versus time response, or the other way around. Fault injection circuit 34 provides the test signal.
    [0024] [0024] Remote diagnostic software 42 has software instructions that are adapted to (1) determine whether there is a fault or an open circuit based on the output of the analog to digital converter 36 and the associated detector 35, and (2) report the fault or the open circuit and a corresponding associated node identifier for the diagnostic tool 10 via the main network structure 16 (as long as the main network structure is functional), via the auxiliary data bus (e.g. , redundant CAN data bus) or via an alternating wired communications system or a wireless communication system.
    [0025] [0025] The diagnostic tool 10 may comprise an electronic data processing system (eg, computer) with a user interface 14 that is coupled to the communications network 26 via a main structure of the network 16 for identifying the location of faults or open circuits. The diagnostic tool 10 can comprise primary diagnostic software 12 which can communicate with remote diagnostic software 42 on one or more network elements (28, 30, 32) coupled to the communications network 26 via a network data bus 16, an auxiliary data bus, or via a spare wire line connection (eg Ethernet, Universal Series Bus (USB), parallel or serial ports of the diagnostic tool 10 and controller 38 connected with power cables) null modem, or vice versa) between data ports of the diagnostic tool 10 and the corresponding network elements. User interface 14 comprises one or more of the following: a display, a keyboard, a key pad, a switch, and a pointing device (e.g., a mouse or electronic rolling ball).
    [0026] [0026] A diagnostic tool 10 determines whether a fault connection between network data bus 16 and a network device 26 exists to report (eg, display a visual or audible alert) to a user via the interface user 14. A fault connection results in the aggregate level detected exceeding at least one of the normal high logic level and the normal low logic level.
    [0027] [0027] In an illustrative example, shown in Fig. 1, the network elements can comprise a first network element 28, a second network element 30, up to an N-th network element 32, where N is any integer positive greater than 2. The first network element 28 is coupled to a network data bus 17 (eg, CAN data bus) or main structure of network 16 at the first node 18. The fault injection circuit 34 of the first network element 28 facilitates injection of the test signal into a first node 18. A detector 35 (eg, voltage level detector), the first network element 28 or the first network element device 44, is capable of sensing a signal level (eg voltage level) on the secondary transmission line 24 at the first node 18. A data processor 48 is adapted to determine that an open circuit fault connection exists between the first network 28 and network data bus 17 on first node 18 if the level of the sensed aggregate violates a reference value or exceeds at least one of the normal high logic level and the normal low logic level.
    [0028] [0028] The second network element 30 is coupled to a network data bus 17 (eg, CAN data bus) or the main structure of network 16 on a second node 20, The second network element 30 is equipped with a transceiver 46, a controller 38, a detector 35, an analog to digital converter 36, and a fault injection circuit 34. The second network element 30 comprises a second network element device 244 comprising the transceiver 46 coupled to controller 38.
    [0029] [0029] Fault injection circuit 34 of the second network element 30 facilitates injection of the test signal into a second node 20. Detector 35 (eg voltage level detector) of the second network element 30 or second network element device 244, is capable of sensing a signal level (e.g. voltage level) on the secondary transmission line 24 on the second node 20. Data processor 48 on the second network element device 244 is arranged to determine that a fault or open circuit connection exists between the second network element 30 and the network data bus 17 or the main structure of the network 16 at the second node 20 if the detected aggregate level violates a reference value, or exceeds at least one of the normal high logic level or and the normal low logic level.
    [0030] [0030] The N-th network element 32 is coupled to the network data bus 17 or to the main structure of network 16 on an N-th node 22. The N-th network element 32 is equipped with a transceiver 46, a controller 38, a detector 35, an analog to digital converter 36, and a fault injection circuit 34. The N-th network element 32 comprises an N-th network element device 144 comprising transceiver 46 coupled to controller 38.
    [0031] [0031] The fault injection circuit 34 of the N-th network element 32 facilitates injection of the test signal in an N-th node 22. Detector 35 (eg voltage level detector) of the N-th network element 32 or N-th network element device 144, is capable of sensing a signal level (e.g., voltage level) on the secondary transmission line 24 on the N-th node 22. The data processor 48 on the N-th network element device 144 is arranged to determine that a fault or open circuit connection exists between the N-th network element 32 and the network data bus 17 or the main structure of network 16 on the N- th node 22 if the level of sensed aggregate violates a reference value, or exceeds at least one of the normal high logic level and the normal low logic level.
    [0032] [0032] Each of the mentioned (s) one or more network elements (28, 30, 32) comprises a corresponding fault injection circuit (eg 34) and a corresponding voltage level detector 35 (eg voltage level detector). The corresponding fault injection circuit 34 is configured or adapted to inject the test signal on a node-by-node basis on each node of the network data bus 17 or main structure of the network 16 on the network 26.
    [0033] [0033] The corresponding detector 35 (eg voltage level detector) senses the voltage level detected on a node-to-node basis (18, 20, 22) at each node of the network data bus 17 in the network 26, where each node is formed on the attempted connection or connection of a network element or network element device to a network data bus 17. A transceiver 46 on each network element is arranged or adapted to report the aggregate level sensed by each node for the diagnostic tool 10 coupled to the data bus 17, or via an auxiliary data bus.
    [0034] [0034] In one configuration, each node (eg 18, 20, 22) is assigned a different test time period by the diagnostic tool 10 or by a controller 38 (eg master controller on a node which communicates with slave controllers on other nodes, where master - slave configurations are programmable or user selectable) on a network 26. For example, each node is assigned a different test time period within a periodic interval or regular break. Each fault injection circuit 34 at each node has instructions or receives a trigger signal to inject the test signal at periodic or regular intervals during operation of the network data bus 17.
    [0035] [0035] FIG. 2 illustrates a method for detecting a fault or an open circuit in a network 26. The method in Fig. 2 starts at step S100,
    [0036] [0036] In step S100, network 26 is operated or provided with a network data bus 17 that has a normal high logic level and a normal low logic level consistent with a termination circuit signal applied by one or more elements of network (28, 30, 32) of network 26. In one configuration, network data bus 17 comprises a Controller Area Network (CAN) data bus, where the normal high logic level is approximately 3.5 volts direct current (DC) and the normal logic level is approximately 1.5 volts direct current (DC).
    [0037] [0037] In step S102, a network element device (eg, 44, 144, or 244), a fault injection circuit 34, or a transceiver 46 injects a test signal into a network data bus 17 from network 26 over a test time period. The test signal has at least one of a higher logic level, greater than the normal high logic level of the network data bus 17 or a lower logic level, less than the normal low logic level of the network data bus 17 In one configuration, the transport media data bus 16 comprises a Network Area Controller (CAN) transport media / data bus 16, the test signal has a higher logic level, equal to approximately 5 volts of direct current (DC) and a lower logic level equal to approximately 0 volts of direct current (DC).
    [0038] [0038] Step S102 can be performed according to various techniques, which can be applied alternatively or cumulatively. In a first technique, a first network element 28, a fault injection circuit 34, or a transceiver 46 injects the test signal into a first node 18 where a first network element 28 is coupled to a network data bus 17 via a secondary transmission line 24 (e.g., one end connected to a network data bus 17). In a second technique, a second network element 30, a fault injection circuit 34, or a transceiver 46 injects the test signal into a second node 20, where the second network element 30 is coupled to a data bus. network 17 via secondary transmission line 24. In a third technique, an N-th network element 32, a fault injection circuit 34, or a transceiver 46 inject the test signal into an N-th node 20, where the N-th network element 32 is coupled to a network data bus 17 via the secondary transmission line 24. In a fourth technique, each network element (28, 30, 32), a fault injection circuit 34 , or a transceiver 46 serially injects, or in a sequential order, the test signal at each node on a node-to-node basis on the secondary transmission line 24 or tip, where each network element is coupled to a data bus. network 17. In a fifth technique, the network element (28, 30, 32), fault injection circuit 34, or trans ceptor 46 inject the test signal at periodic or regular intervals during operation of the data bus 17.
    [0039] [0039] In step S104, during the test time period, the network element (28, 30, 32) or detector 35 (eg, a voltage level detector) senses an aggregate level of an aggregate signal on a network data bus 17. The aggregate signal is composed of the terminating circuit signal and the test signal. Step S104 can be performed according to various techniques, which can be applied alternatively or cumulatively. In a first technique, the first network element 28 or a detector 35 (eg, voltage level detector) senses or detects the voltage level or logic levels on a network data bus 17 on the first node 18. In a second technique, the second network element 30 or detector 35 (eg, voltage level detector) senses or detects the voltage level or logic levels at the second node 20. In a third technique, the N-th network 32 or detector 35 (eg, a voltage level detector) senses or detects, serial or sequentially, the voltage levels or logic levels at each node on a network data bus 17 on a node-by-node basis . In a fourth technique, the network element (28, 30, 32) or a detector 35 senses or detects a voltage level or logic levels on a network data bus 17 at periodic or regular intervals during operation of the data bus. network 17.
    [0040] [0040] In step S105, the network element (28, 30, 32), the network element device (44, 144, 244), or data processor 48 determines whether the detected aggregate level exceeds the logical level high normal, logic level low normal, or both (eg, in terms of absolute value) over a period of test time. For example, in step S105 the network element (28, 30, 32), the network element device (44, 144, 244), or the data processor 48 can evaluate the absolute value of the detected aggregate level and the corresponding absolute value of the normal high logic level and the corresponding absolute value of the normal low logic level to make the above determination. If the network element (28, 30, 32), the network element device (44, 144, 244), or the data processor 48 determines that the detected aggregate level exceeds the normal high logic level, the logical level normal low, or both during the test time period, then the method continues with step S106. However, if the network element (28, 30, 32), the network element device (44, 144, 244), or data processor 48 determines that the level of sensed aggregate does not exceed the normal high logic level or the normal low logic level (eg, on an absolute value basis) during the test time period, then the method continues with step S107.
    [0041] [0041] Step S105 can be performed according to various techniques that can be applied separately or cumulatively. In a first technique for performing step S105, the network element (28, 30, 32), the network element device (44, 144, 244), or data processor 48 determines whether the level of sensed aggregate is greater than the normal high logic level (eg, a positive DC voltage) or less than the normal low logic level (eg, zero volts or a negative DC voltage) during a test time period, such that either the higher or lower level of sensed aggregate exceeds the normal high logic level or the normal high logic level.
    [0042] [0042] In a second technique to perform step S105, transceiver 46 or network element (28, 30, 32) reports the level of sensed aggregate, or derivative data derived from them, by each node to a coupled diagnostic tool 10 to the network data bus 17, where the network element (28, 30, 32), the network element device (44, 144, 244) or data processor 48 forms the derivative data to indicate whether the level of sensed aggregate exceeds at least one of the normal high logic level and the normal low logic level (eg, on an absolute value basis).
    [0043] [0043] In a third technique, the diagnostic tool 10 or network element device (eg controller 38 configured as a master controller) assigns each node to a different test time period by the diagnostic tool 10 or a master controller 38 on network 26, where the network element (28, 30, 32), the network element device (44, 144, 244). In addition, data processor 48 forms derivative data to indicate whether the sensed aggregate level exceeds at least one of the normal high level and the normal low logic level (eg, on an absolute value basis) for transmission (eg ., via a network element device or transceiver 46) during its designated test time period.
    [0044] [0044] In a fourth technique, the diagnostic tool 10 or network device 26 (eg controller 38 configured as a master controller) assigns each node a different test time period within a periodic or regular interval. In addition, data processor 48 forms derivative data to indicate whether the detected aggregate level exceeds at least one of the normal high level and the normal low logic level (eg, on an absolute value basis) for transmission (eg ., by a network element device or transceiver 46) during the designated periodic or regular interval.
    [0045] [0045] In step S106, the network element (28, 30, 32), the network element device (44, 144, 244), or a data processor 48 of the network device 26 determines that a failed connection (eg, open circuit or intermittent connection) between network data bus 17 and a network element (28, 30, 32) exists, where a fault connection results in the detected aggregate level violating a reference value, such as exceeding at least one of the normal high logic level and the normal low logic level (eg, on an absolute value basis). Step S106 can be performed according to various techniques, which can be applied alternatively or cumulatively. In a first technique, the first network element device 44, or a data processor 48 of the first network element device 44 on the first node 18, determines that a fault connection exists between the first network device 26 and the bus network data 17 if the sensed aggregate level exceeds at least one of the normal high logic level and the normal low logic level (eg, on an absolute value basis).
    [0046] [0046] In a second technique, a second network element device 244, a data processor 48 of the second network element device 244 on a second node 20 determines that a fault connection exists between the second network element device 244 and the network data bus 17 if the sensed aggregate level exceeds at least one of the normal high logic level and the normal low logic level (eg, on an absolute value basis).
    [0047] [0047] In a third technique, an Nth network element device 144, a data processor 48 of the Nth network element device 144 on a second node 20 determines that a fault connection exists between the N- th network element device 144 and the network data bus 17 if the sensed aggregate level exceeds at least one of the normal high logic level and the normal low logic level (e.g., on an absolute value basis).
    [0048] [0048] In a fourth technique, each network element device (44, 144, 244), a data processor 48 of each network element device (44, 144, 244) on a node (18, 20, 22 ) determines serially or sequentially on a node-by-node basis that a fault connection exists between each network element device (44, 144, 244) and the network data bus 17 if the detected aggregate level exceeds at least one normal high logic level and normal low logic level.
    [0049] [0049] In step S107, the network element (28, 30, 32), the network element device (44, 144, 244), or a data processor 48 of the network device 26 determines that a failed connection it is not sensed between the data bus and a network device (eg at the respective node where the test signal is injected).
    [0050] [0050] FIG. 3 illustrates a sequence diagram or data flow associated with various diagnostic related processes including the following: (a) data flow to obtain metrics in block 300, (b) data flow for a failure injection test in block 340, and (c) data flow to adjust diagnostic metrics in block 380,
    [0051] [0051] In block 300, the diagnostic tool 10 obtains metrics by querying the network element device on the first node 18 and the second node 20 to diagnose data or metrics. For example, diagnostic tool 10 can send a request to all nodes (eg, common broadcast message) or sequentially query each node on a node-by-node basis to report diagnostic data to diagnostic tool 10 on the network 26. The request to query diagnostic metrics 302 is transmitted to a first node 18 and a second node 20. Each network controller 38 can individually respond to the request with diagnostic data within a designated communication time period, in a time division multiplex base, a frequency division multiplex base, a containment base, according to multiple carrier sensing access (CSMA), in a sequential order, according to the ALOHA protocol or ALOHA protocol spaced in time, or the other way around. For example, first node 18 can respond to the diagnostic metrics query 302 with a first data message from node 308 that contains current metrics 304. The second node 20 can respond to the diagnostic metrics query with a second data message from node 310 containing current metrics 306.
    [0052] [0052] In block 340, consultation of the diagnostic tool 10 can trigger the activation of a fault injection test through fault injection circuit 34 on the first node 18, by another fault injection circuit 34 on the second node 20, or on another node equipped with fault injection circuit 34. In one configuration, the diagnostic tool 10 listens to or reads network data bus 17 for activity, a QUIET command, or an available bus message. data that indicates that the diagnostic tool 10 can transmit a request for the fault injection test to the node via network data bus 17 without interrupting or interfering with communication traffic via network data bus 17. In In another configuration, the diagnostic tool 10 can transmit or repeat the transmission of a bus QUIET command 342 to the first node 18 and the second node 20.
    [0053] [0053] When the network data bus 17 is available or when the request is received, in block 340 the diagnostic tool can transmit a request or command to conduct the fault injection test 344 to the first node 18. The circuit fault injection 34 injects the test signal into a first node 18 where a first network device 26 is coupled to the network data bus 17. The network element or sensor at the first node 18 senses the test signal with a detector voltage level. If the detected voltage level exceeds a voltage threshold level or a normal logic level for the network data bus 17, the fault connection (eg, open circuit condition) exists between the first network device 26 and the network data bus 17. For example, if the sensed aggregate level exceeds at least one of the normal high logic level and the normal low logic level, the fault connection (eg, open circuit condition) exists between the first network device 26 and network data bus 17 and test results or failure data message and associated node identifier can be reported to diagnostic tool 10 to display on user interface 14 of the data processing system electronic data. First node 18 sends a first node data message 352 of test results 346 to diagnostic tool 10.
    [0054] [0054] When the network data bus 17 is available or when the request is received, in block 340 the diagnostic tool can transmit a request or command to conduct the fault injection test 344 to the second node 20. The circuit fault injection 34 injects the test signal into a second node 20 where a second network device 26 is coupled to the network data bus 17. The network element or sensor at the second node 20 senses the test signal with a detector voltage level. If the sensed voltage level exceeds a voltage threshold level or a normal logic level for the network data bus 17, the fault connection (eg, open circuit condition) exists between the second network device 26 and the network data bus 17. For example, if the aggregate level detected exceeds at least one of the normal high logic level and the normal low logic level, the fault connection (eg, open circuit condition) exists between the second network device 26 and network data bus 17 and the test results or failure data message and associated node identifier can be reported to the diagnostic tool 10 to display on the user interface 14 of the processing system electronic data. The second node 20 sends a second data message from node 354 of test results 350 to the diagnostic tool 10.
    [0055] [0055] In block 380, the diagnostic tool 10 can restart or clear the diagnostics metrics, test results or failure data message and associated node identifier on the node or network device. For example, diagnostic tool 10 can restart or clear diagnostic metrics, test results, or failure data message by sending a command or data message (eg, a translucent diagnostic metrics data message 382) to the first network device on the first node 18 and to the second network device on the second node 20. The data processor 48 within the transceiver 46 or a network device 26 will reconfigure one or more data records or clear the data device data storage 40 of one or more open connection or accumulated failure messages consistent with the command, for example. Transceiver 46 can provide an acknowledgment message (388, 390) of the compensation of the diagnostic metrics on each node (18, 20) in a first node data message 384 and a second node data message 386.
    [0056] [0056] FIG. 4A shows the main structure of the network 16 or data bus (eg, Controller Area Network (CAN) data bus) as it comprises a transmission line 15 of a twisted pair of wires, although the main structure of the network 16 can be implemented as any suitable type of transmission line, including, but not limited to, a coaxial cable, a multi-conductor cable, or an optical cable. A first network element device 28 is coupled to the network data bus 17 on a first node 18 via a secondary transmission line 24 (e.g., tributary twisted pair). A second network element 30 is coupled to the data bus or main structure of the network 16 at a second node 20 via a secondary transmission line 24 (e.g., tributary twisted pair). As illustrated, there is an open or interrupted circuit 77 on the secondary transmission line 24 associated with the second node 20.
    [0057] [0057] FIG. 4B is a diagram showing a waveform and magnitude of signals on the data bus (eg, CAN data bus) or the main structure of network 16 over various time periods, labeled as a first time period 425 , a second time period 426, and a third time period 427. The vertical axis of Fig. 4B indicates voltage or magnitude 404 of the signals on the data bus 17, while the horizontal axis of Fig. 4B indicates time 406. The waveform of Fig. 4B provides an illustration of the sensing of the open or interrupted circuit 77 shown in Fig. 4A, as described in more detail below.
    [0058] [0058] In Fig. 4B, for a first time period 425, a data message packet 408 (eg, CAN message) is transmitted via data bus 17 or the main structure of network 16. For example , the data message packet may comprise a normal data message 410 or other digital data that is transmitted from the first node 18 or the second node 20, or vice versa. Because of the open circuit at the second node 20, the transmission is not effectively communicated (e.g., robust or reliably communicated) between the network device element associated with the first node 18 and the second node 20. The normal data message 410 is consistent with digital logic levels specified for data bus 17, the main structure of network 16 or data network 26. For example, in the first time period 425 the CAN data packet is between a normal low logic level 420 (eg, CAN-low or 1.5 Volts DC) and a normal high logic level 418 (eg, CAN-high or 3.5 Volts DC).
    [0059] [0059] During a 426 second time period, no data message is transmitted. In its place, a test signal is transmitted from the first network element device 44 at a first node 18 and detected by detector 35 from the first network element 28 at the first node 18. The sensed voltage level only results in no major deviation or slight deviation from the DC bias voltage level 421 on a network data bus 17. As illustrated in FIG. 4B, the slight deviation is represented by a slight curvature that approaches a limit above and below the horizontal dashed line indicating the polarization voltage (eg 2.5 Volts DC) of the network data bus 17.
    [0060] [0060] During a third time period 427, no data message is transmitted. In its place, the fault injection circuit 24 transmits a test signal from the second network element 30 of the second node 20. The voltage level detected at detector 35 at the second node 20 results in a significant deviation from the bias voltage of direct current on the data bus, or at least on the secondary transmission line 24. The significant deviation or higher high logic level 416 is illustrated as a generally regular step or waveform function in Fig. 4B. The deviation is possible because of the open circuit that exists at interrupt 77 that is associated with the second node 20. Consequently, at the second node 20, the voltage level detector of the second network element device 30 recognizes the significant deviation, a step function or the generally rectangular waveform such as a fault or an open circuit on the data bus or the connection on the second node 20, or the secondary transmission line 24 on the second node 20, for example.
    [0061] [0061] FIG. 5A and FIG. 5B provides functional status diagrams for the diagnostic software, which can be applicable to any modality of the diagnostic system, such as in Fig. 1. In Fig. 5A, the diagnostic software illustrates states associated with the injection injection test. failure. In block 500, the diagnostic software has a first state in which the software is idle.
    [0062] [0062] In a second state of block 510, the diagnostic tool 10 authorizes or requests a diagnostic test or injection test. A user can connect diagnostic tool 10 (eg, a portable diagnostic tool 10) to the data bus or mainframe network 16 via a secondary transmission line 24 or tip connection and activate a request for a diagnostics via user interface 14, for example.
    [0063] [0063] In block 502, the network element device activates the injection of a test signal in response to the request or authorization of the diagnostic tool 10. After the injection and a possible time delay 513, in a third state in the block 504, the network element device or its diagnostic software is instructed to sample analog voltages on data network 26 or main structure of network 16 (e.g., data bus). A possible time delay 513 follows block 504.
    [0064] [0064] In block 506 in a fourth state after the injection of the test signal is completed, the network element device or the diagnostic software disables the injection of the test signal. A possible time delay 513 follows block 506.
    [0065] [0065] In block 508 in a fifth state, the test results are transmitted from the network element device to the diagnostic tool 10 via the network 26 or data bus. Alternatively, the test results are transmitted from the network element device to the diagnostic tool via a secondary wire line interface or a wireless interface, if network 26 or network data bus 17 does not support transmission reliable data because of a failure or condition. No delay 515 follows block 508, where the state returns to idle computing system 500.
    [0066] [0066] FIG. 5B is similar to Fig. 5A, except that the first state in block 514 is different from that in the first state in block 510 of Fig. 5A and the fifth state in block 512 of Fig. 5B is different from that in the fifth state of block 508 of Fig. 5A. Similar states, procedures or blocks in Fig. 5A and FIG. 5B are indicated by similar reference numbers.
    [0067] [0067] The state diagram of Fig. 5B is oriented towards a self-activated diagnostic test, as opposed to a user-activated diagnostic test from a user interface 14, consistent with Fig. 5A. For example, in Fig. 5B the diagnostic tool 10 can be disconnected from the data bus, at least temporarily or the user interface 14 can be inactive.
    [0068] [0068] In block 514 of Fig. 5B a network element (28, 30, 32), a fault injection circuit 34, or a data processor 48 detects an error (eg, a CAN error) via logical algorithm (eg, pattern recognition in one or more error codes, such as a trigger event, which indicates a diagnostic test or injection of a test signal is guaranteed). In block 514, a network element (28, 30, 32), a fault injection circuit 34, or a data processor 48 can trigger activation of injection in block 502 through a trigger event such as an occurrence of a or more of the following: the lapse of time, the expiration of a time counter, at a programmed time, programmed by a user via user interface 14, a periodic test, detection of one or more errors (e.g. , CAN data bus error messages) detected by controller 38, transceiver 46, or the network element.
    [0069] [0069] In block 512, the fifth state of Fig. 5B, the test results are stored for later dissemination and disseminated when a suitable transmission path is available between the network element and the diagnostic tool 10. The transmission path suitable can link a data bus, or via a secondary wire line interface or a wireless interface, for example.
    [0070] [0070] Having described the preferred modality, it will become clear that several modifications may be made without departing from the scope of the invention as defined in the appended claims.
    权利要求:
    Claims (15)
    [0001]
    Method for diagnosing a fault or an open circuit in a network (26) that has network elements (28, 30, 32) and data bus (17) that has a normal high logic level and a normal low logic level consistent with a termination circuit signal applied by one or more network elements (28, 30, 32) of the network (26) to the data bus (17), the method characterized by the fact that it comprises: operating a data bus (17) from a network (26); inject a test signal into the network data bus (17) (26) for a period of test time, the test signal having at least one of a higher logic level, greater than the normal high logic level of the bus. data (26) or a lower logic level, lower than the normal low logic level of the data bus (26); during the test time period, sensing an aggregate level of an aggregate signal on the data bus (26), the aggregate signal composed of the termination circuit signal applied by one or more of the network elements (28, 30, 32 ) from the network (26) to the data bus (17) and the test signal; and determine whether a fault connection between the data bus (17) and a network device (28, 30, 32) exists, where a fault connection results in the sensed aggregate level exceeding at least one of the normal high logic level and the normal low logic level.
    [0002]
    Method according to claim 1, characterized by the fact that: the injection comprises injecting the test signal into a first node (18), where a first network device (28) is coupled to the data bus (17), - detection comprises sensing at the first node (18), and - the determination comprises determining in the first node (18) or in a diagnostic tool (10), coupled to the data bus (17), that the fault connection exists between the first network device (18) and the data bus (17) if the level of sensed aggregate exceeds at least one of the normal high logic level and the normal low logic level.
    [0003]
    Method according to claim 2, characterized by the fact that: the injection comprises injecting the test signal into a second node (20), where a second network device (30) is coupled to the data bus (17), the sensing comprises sensing at the second node (20), and the determination comprises determining at the second node (20) or in a diagnostic tool (10), coupled (a) to the data bus (17), that the fault connection exists between the second network device (30) and the bus (17), if the level of sensed aggregate exceeds at least one of the normal high logic level and the normal low logic level.
    [0004]
    Method according to claim 1, characterized by the fact that: injection and sensing are repeated on a node-by-node basis at each node (18, 20, 22) of the data bus (17) in a network (26), where each node (18, 20, 22) is formed connecting or tentatively connecting a network device (28, 30, 32) to the data bus (17); report the level of aggregate sensed by each node (18, 20, 22) to a diagnostic tool (10) coupled to the data bus (17).
    [0005]
    Method according to claim 4, characterized in that each node (28, 30, 32) is assigned to a different test time period by the diagnostic tool (10) or a master controller in a network (26).
    [0006]
    Method according to claim 5 characterized by the fact that each node (18, 20, 22) is assigned a different test time period within a periodic or regular interval.
    [0007]
    Method according to claim 1, characterized in that the injection occurs at periodic or regular intervals during the operation of the data bus (17).
    [0008]
    Method according to claim 1, characterized by the fact that the data bus (17) comprises a Controller Area Network data bus, and in which the test signal has a higher logic level, equal to approximately 5 volts of direct current and a lower logic level equal to approximately 0 volts of direct current, and that the normal high logic level is approximately 3.5 volts of direct current and the normal logic level is approximately 1.5 volts of direct current.
    [0009]
    System (11) for diagnosing a fault or an open circuit in a network (26), the system comprising: a network (26) comprising a data bus (17) and one or more network elements (28, 30, 32), the data bus (17) having a normal high logic level and a normal low logic level consistent with a termination circuit signal applied by said one or more network elements (28, 30, 32) of the network; the system characterized by: a fault injection circuit (34) to inject a test signal into the data bus (17) of the network (26), via a pull-up resistor with a high impedance with respect to the data bus, during a period of test time, the test signal having at least one of a higher logic level, greater than the normal high logic level of the data bus (17) or a lower logic level, less than the normal low logic level of the data bus data (17); an analog to digital converter (36) coupled to a voltage level detector (35) to sense an aggregate level of an aggregate signal on the data bus (26), the aggregate signal composed of the termination circuit signal applied by one or more of the network elements (28, 30, 32) of the network (26) to the data bus (17) and the test signal; a diagnostic tool (10) to determine whether a fault connection between the data bus (17) and a network device (28, 30, 32) exists, where a fault connection results in the sensed aggregate level exceeding at least one of the normal high logic level and the normal low logic level.
    [0010]
    System (11) according to claim 9, characterized by the fact that: a first network device (28) coupled to the data bus at the first node (18), the first network device comprising one of the mentioned (s) one or more network elements; the fault injection circuit (34) of the first network device facilitating injection of the test signal in a first node (18); a voltage level detector (35), of the first network device (28), adapted to sense a voltage level at the first node (18); and a data processor (48) adapted to determine that a failed connection exists between the first network device (28) and the data bus (17) on the first node (18) if the level of sensed aggregate exceeds at least one of the normal high logic level and normal low logic level.
    [0011]
    System (11) according to claim 10, characterized in that it additionally comprises: a second network device (30) coupled to the data bus (17) at a second node (20), the second network device comprising one of the said (s) one or more network elements; a second fault injection circuit (34) of the second network device (30) facilitating injection of the test signal into a second node (20); a second voltage level detector (35), of the second network device (30), for sensing a voltage level at the second node (20); and a second data processor (48) to determine that a failed connection exists between the second network device (30) and the data bus (17) on the second node (20) if the level of sensed aggregate exceeds at least one of the normal high logic level and normal low logic level.
    [0012]
    System (11) according to claim 9, characterized by the fact that: each of the mentioned (s) one or more network elements (28, 30,32) comprises a corresponding fault injection circuit (34) and a corresponding voltage level detector (35); the corresponding fault injection circuit (34) configured or adapted to inject the test signal on a node-by-node basis on each node (18, 20, 22) of the data bus (17) in a network (26); the corresponding voltage level detector (35) adapted to sense the voltage level detected on a node-by-node basis at each node (18, 20, 22) of the data bus (17) in a network (26), where each node (18, 20, 22) is formed in the connection or tentative connection of a network device (28, 30, 32) to the data bus (17); and a transceiver (46) on each network device (28, 30, 32) adapted to report the level of aggregate sensed by each node (18, 20, 22) to the diagnostic tool (10) coupled to the data bus (17 ).
    [0013]
    System (11) according to claim 12 characterized by the fact that each node (18, 20, 22) is assigned a different test time period by the diagnostic tool 910) or a master controller in the network (26).
    [0014]
    System (11) according to claim 13, characterized by the fact that each node (18, 20, 22) is assigned a different test time period within a periodic or regular interval.
    [0015]
    System (11) according to claim 9, characterized by the fact that each fault injection circuit (34) at each node (18, 20, 22) has instructions or receives a trigger signal to inject the test signal in periodic or regular intervals during data bus operation (17).
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112013015404B1|2020-09-24|METHOD AND SYSTEM FOR DIAGNOSING A FAILURE OR AN OPEN CIRCUIT ON A NETWORK
    US9568533B2|2017-02-14|Method and apparatus for open-wire fault detection and diagnosis in a controller area network
    US9524222B2|2016-12-20|Method and apparatus for fault detection in a controller area network
    US9384085B2|2016-07-05|Method, device, and system for monitoring quickpath interconnect link
    US6357018B1|2002-03-12|Method and apparatus for determining continuity and integrity of a RAMBUS channel in a computer system
    US7861110B2|2010-12-28|System, method, and adapter for creating fault-tolerant communication busses from standard components
    US9678131B2|2017-06-13|Method and apparatus for short fault isolation in a controller area network
    CN105319474B|2019-12-31|Method and apparatus for short circuit fault detection in controller area networks
    US9110951B2|2015-08-18|Method and apparatus for isolating a fault in a controller area network
    US20150312123A1|2015-10-29|Method and apparatus for isolating a fault in a controller area network
    TW201719436A|2017-06-01|Method of detecting fault on communication bus using baseboard management controller and fault detector for network system
    JP2015136104A5|2018-02-01|
    US11245547B2|2022-02-08|Monitoring controller area network | nodes
    KR20120132631A|2012-12-06|Determination of physical connectivity status of devices based on electrical measurement
    CN112306766A|2021-02-02|Method, electronic device, storage system and computer program product for error detection
    CN103885441A|2014-06-25|Self-adaptive fault diagnosis method for controller local area network
    US7788546B2|2010-08-31|Method and system for identifying communication errors resulting from reset skew
    US10199773B2|2019-02-05|Systems and methods for automatic detection of misconnected cables
    JP3654823B2|2005-06-02|Transmitter / receiver unit in two-wire bus
    US11283646B2|2022-03-22|Monitoring local interconnect network | nodes
    US20200274734A1|2020-08-27|Monitoring local interconnect network | nodes
    CN106487456A|2017-03-08|Communication test device, system and method
    CN111858222A|2020-10-30|Error injection method, apparatus, data storage system and program product
    同族专利:
    公开号 | 公开日
    US8699356B2|2014-04-15|
    EP2656088A1|2013-10-30|
    JP2014505411A|2014-02-27|
    CN103328992A|2013-09-25|
    EP2656088B1|2016-06-15|
    WO2012087808A1|2012-06-28|
    AU2011349611B2|2015-12-24|
    AU2011349611A1|2013-07-11|
    BR112013015404A2|2016-09-20|
    EP2656088A4|2015-08-05|
    CN103328992B|2016-01-20|
    US20120155285A1|2012-06-21|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US4521848A|1978-10-31|1985-06-04|Honeywell Information Systems Inc.|Intersystem fault detection and bus cycle completion logic system|
    US4266292A|1978-11-20|1981-05-05|Wescom Switching, Inc.|Method and apparatus for testing analog-to-digital and digital-to-analog code converters|
    US4376999A|1980-06-03|1983-03-15|Rockwell International Corporation|Muldem with monitor testing on-line and off-line paths|
    US4395767A|1981-04-20|1983-07-26|Control Data Corporation|Interconnect fault detector for LSI logic chips|
    US4825438A|1982-03-08|1989-04-25|Unisys Corporation|Bus error detection employing parity verification|
    US4841232A|1988-04-29|1989-06-20|International Business Machines Corporation|Method and apparatus for testing three state drivers|
    US4951283A|1988-07-08|1990-08-21|Genrad, Inc.|Method and apparatus for identifying defective bus devices|
    JP3005250B2|1989-06-30|2000-01-31|テキサスインスツルメンツインコーポレイテツド|Bus monitor integrated circuit|
    US5066919A|1990-04-03|1991-11-19|Ford Motor Company|Fault detection and isolation in automotive wiring harness by network analysis method|
    US5373514A|1990-09-20|1994-12-13|Synopsys, Inc.|Three-state bus structure and method for generating test vectors while avoiding contention and/or floating outputs on the three-state bus|
    US5691976A|1992-04-02|1997-11-25|Applied Digital Access|Performance monitoring and test system for a telephone network|
    DE4211579C1|1992-04-07|1993-11-18|Daimler Benz Ag|Method for monitoring symmetrical two-wire bus lines and bus interfaces, and device for carrying out the method|
    US5390326A|1993-04-30|1995-02-14|The Foxboro Company|Local area network with fault detection and recovery|
    US5477529A|1994-09-29|1995-12-19|Alcatel Network Systems, Inc.|ISDN signal transmission performance monitoring|
    US5530360A|1994-12-09|1996-06-25|Chrysler Corporation|Apparatus and method for diagnosing faults in a vehicle electrical system|
    JP3607760B2|1995-10-13|2005-01-05|富士通株式会社|Semiconductor integrated circuit device|
    DE19752792B4|1997-11-28|2004-04-15|Phoenix Contact Gmbh & Co. Kg|Device for self-diagnosis of essentially sporadic errors in serial transmission systems|
    US7583587B2|2004-01-30|2009-09-01|Microsoft Corporation|Fault detection and diagnosis|
    US7599299B2|2004-04-30|2009-10-06|Xilinx, Inc.|Dynamic reconfiguration of a system monitor |
    US7577212B2|2004-08-30|2009-08-18|Micron Technology, Inc.|Method and system for generating reference voltages for signal receivers|
    US7337086B2|2005-10-18|2008-02-26|Honeywell International, Inc.|System and method for combining diagnostic evidences for turbine engine fault detection|
    US7514937B2|2005-11-21|2009-04-07|Sun Microsystems, Inc.|Method and apparatus for interconnect diagnosis|
    CN2894106Y|2006-04-19|2007-04-25|哈尔滨工程大学|Computer network credibility estimating device based on event implanting|
    US7952360B2|2007-03-14|2011-05-31|General Electric Company|Method and system for passively detecting and locating wire harness defects|
    CN101042420B|2007-04-24|2010-05-26|华为技术有限公司|Method, system and device for line detection|
    CN100546262C|2007-07-04|2009-09-30|北京航空航天大学|A kind of broadband aviation electronic bus testing apparatus and method of operation thereof|
    US8527374B2|2008-03-21|2013-09-03|Rochester Institute Of Technology|Method and apparatus for data acquisition in an asset health management system|
    CN101334754A|2008-08-05|2008-12-31|浙江大学|Fault infusion based embedded system evaluation method|
    US8667123B2|2008-09-29|2014-03-04|Woodhead Industries, Inc.|Microcontroller network diagnostic system|
    US7999667B2|2009-01-07|2011-08-16|The Boeing Company|Vehicle health management system|US9003292B2|2006-07-06|2015-04-07|LiveAction, Inc.|System and method for network topology and flow visualization|
    US9673609B2|2012-02-21|2017-06-06|Hamilton Sundstrand Corporation|Self-test of over-current fault detection|
    US9673611B2|2012-02-21|2017-06-06|Hamilton Sundstrand Corporation|Self-test of over-current fault detection|
    US8645020B2|2012-06-21|2014-02-04|Freescale Semiconductor, Inc.|Channel diagnostic system for sent receiver|
    JP6036073B2|2012-09-19|2016-11-30|富士通株式会社|Transmission unit, diagnostic method and diagnostic program|
    US20150081243A1|2013-03-20|2015-03-19|Nec Laboratories America, Inc.|Setsudo: Pertubation-based Testing Framework for Scalable Distributed Systems|
    CN103259686B|2013-05-31|2016-04-27|浙江大学|Based on the CAN network fault diagnosis method of isolated errors event|
    CN103475523B|2013-09-10|2016-04-27|浙江大学|With the CAN analytical system of bus error analytical capabilities|
    JP6187086B2|2013-09-20|2017-08-30|富士通株式会社|Information processing apparatus, communication method, and communication program|
    US9082242B2|2013-10-11|2015-07-14|GM Global Technology Operations LLC|Vehicle network health assessment|
    GB2519353A|2013-10-18|2015-04-22|St Microelectronics Res & Dev|Testing method, testing apparatus and circuit for use with scan chains|
    DE102014207190A1|2014-04-15|2015-05-13|Siemens Schweiz Ag|Error detection by trigger object|
    US8930067B1|2014-05-05|2015-01-06|Nmtc, Inc.|System and method for a subscription-based diagnostic software service|
    US9678131B2|2014-05-27|2017-06-13|GM Global Technology Operations LLC|Method and apparatus for short fault isolation in a controller area network|
    US9641070B2|2014-06-11|2017-05-02|Allegro Microsystems, Llc|Circuits and techniques for detecting an open pin condition of an integrated circuit|
    KR102262081B1|2015-09-08|2021-06-07|현대자동차주식회사|Compliance test apparatus and method of communication node|
    US10367612B2|2015-09-30|2019-07-30|Rosemount Inc.|Process variable transmitter with self-learning loop diagnostics|
    US10048302B2|2016-02-15|2018-08-14|Ford Global Technologies, Llc|Vehicle communications signal diagnostics using radio receiver|
    EP3208621A1|2016-02-18|2017-08-23|Siemens Aktiengesellschaft|Cable break in modular systems|
    US9965378B1|2016-03-29|2018-05-08|Amazon Technologies, Inc.|Mediated fault invocation service|
    US10647369B2|2016-10-07|2020-05-12|Phillips Connect Technologies Llc|Modular harness system|
    CN106556769B|2016-11-22|2019-02-19|北京润科通用技术有限公司|Direct fault location circuit, method and device|
    US10768228B2|2018-04-05|2020-09-08|Nxp B.V.|Communication circuitry integrity assessment|
    DE102018122873A1|2018-09-18|2020-03-19|Göpel electronic GmbH|Procedure for checking the behavior of bus participants on a CAN FD bus in accordance with specifications|
    JP2020142646A|2019-03-06|2020-09-10|トヨタ自動車株式会社|Communication failure detection device|
    US11233713B2|2019-07-19|2022-01-25|Deere & Company|Controller area network and connectivity health troubleshooting system|
    CN111308922B|2019-07-30|2021-01-15|厦门雅迅网络股份有限公司|Method for preventing CAN bus from sending error frame and CAN bus equipment|
    法律状态:
    2018-12-18| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2019-07-16| B06T| Formal requirements before examination [chapter 6.20 patent gazette]|
    2020-05-26| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2020-09-24| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 16/12/2011, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US201061424926P| true| 2010-12-20|2010-12-20|
    US61/424926|2010-12-20|
    US13/099,455|US8699356B2|2010-12-20|2011-05-03|Method and system for diagnosing a fault or open circuit in a network|
    US13/099455|2011-05-03|
    PCT/US2011/065451|WO2012087808A1|2010-12-20|2011-12-16|Method and system for diagnosing a fault or open circuit in a network|
    [返回顶部]